Techniques for providing dynamic account and device management

ABSTRACT

Techniques for providing data in dynamic account and device management are disclosed. In one particular exemplary embodiment, the techniques may be realized as a system for providing data in dynamic account and device management. The system may comprise one or more processors communicatively coupled to a network. The one or more processors may be configured to identify a user device to be managed. The one or more processors may be configured to transmit a request for delegate authority to manage the user device. The one or more processors may be configured to receive delegate authority to manage the user device. The one or more processors may be configured to provide network access to the user device. The one or more processors may also be configured to manage the user device and monitor data communicated to and from the user device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of U.S. patent applicationSer. No. 13/524,795, filed Jun. 15, 2012, now U.S. Pat. No. 8,984,111,which is hereby incorporated by reference herein in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to systems management and, moreparticularly, to techniques for providing dynamic account and devicemanagement.

BACKGROUND OF THE DISCLOSURE

More and more companies are allowing employees to bring their personalcomputing devices to work and use them in the work environment. Managingthese personal devices and monitoring data communicated using thesedevices within a corporate setting are becoming increasinglychallenging, especially across multiple management systems and multipleaccounts.

In view of the foregoing, it may be understood that there may besignificant problems and shortcomings associated with conventionalaccount and device management technologies as applied to personalcomputing devices used in a corporate infrastructure.

SUMMARY OF THE DISCLOSURE

Techniques for providing dynamic account and device management aredisclosed. In one particular exemplary embodiment, the techniques may berealized as a system for providing data in dynamic account and devicemanagement. The system may comprise one or more processorscommunicatively coupled to a network. The one or more processors may beconfigured to identify a user device to be managed. The one or moreprocessors may be configured to transmit a request for delegateauthority to manage the user device. The one or more processors may beconfigured to receive delegate authority to manage the user device. Theone or more processors may be configured to provide network access tothe user device. The one or more processors may also be configured tomanage the user device and monitor data communicated to and from theuser device.

In accordance with other aspects of this particular embodiment, the userdevice may be a personal user device associated with a personal useraccount. In some embodiments, the personal user account may comprise atleast one of an Internet-based account, a cloud-accessible account, andan enterprise-compatible account. In some embodiments, the delegateauthority may be granted by a primary accountholder of via the personaluser account.

In accordance with further aspects of this particular embodiment,identifying the user device to be managed may comprise receiving arequest by a user of the user device for network access.

In accordance with additional aspects of this particular embodiment,identifying the user device to be managed may comprise detecting theuser device within range of the network.

In accordance with other aspects of this particular embodiment, therequest for delegate authority may comprise at least one of an email, atext message, an instant message, a phone call, a voicemail, a website,a uniform resource locator (URL) link, and a menu window.

In accordance with further aspects of this particular embodiment,network access may comprise network access to at least one of acorporate network, enterprise network, residential network, and privatenetwork.

In another particular embodiment, the techniques may be realized as amethod for providing dynamic account and user device management. Themethod may comprise identifying, using a computer, a user device to bemanaged. The method may comprise transmitting a request for delegateauthority to manage the user device. The method may comprise receivingdelegate authority to manage the user device. The method may compriseproviding network access to the user device. The method may comprisemanaging the user device and monitor data communicated to and from theuser device.

In accordance with other aspects of this particular embodiment, the userdevice may be a personal user device associated with a personal useraccount comprising at least one of: an Internet-based account, acloud-accessible account, and an enterprise-compatible account.

In accordance with further aspects of this particular embodiment,identifying the user device to be managed may comprise at least one of:receiving a request by a user of the user device for network access, anddetecting the user device within range of the network;

In accordance with additional aspects of this particular embodiment, therequest for delegate authority may comprise at least one of: an email, atext message, an instant message, a phone call, a voicemail, a website,a uniform resource locator (URL) link, and a menu window.

In accordance with other aspects of this particular embodiment, networkaccess may comprise network access to at least one of: a corporatenetwork, enterprise network, residential network, and private network.

In another particular embodiment, the techniques may be realized as asystem for providing dynamic account and user device management. Thesystem may comprise one or more processors communicatively coupled to anetwork. The one or more processors may be configured to receive arequest for delegate authority by an entity to manage a user device. Theone or more processors may be configured to transmit informationrequired to provide delegate authority to manage the user device. Theone or more processors may be configured to receive network access atthe user device, wherein the entity manages the user device and monitorsdata communicated to and from the user device.

In accordance with other aspects of this particular embodiment, the userdevice may be a personal user device associated with a personal useraccount. In some embodiments, the personal user account may comprise atleast one of an Internet-based account, a cloud-accessible account, andan enterprise-compatible account. In some embodiments, the delegateauthority may be granted by a primary accountholder of via the personaluser account.

In accordance with further aspects of this particular embodiment, thesystem may provide identity of the user device to be managed byreceiving a request by a user of the user device for network access ordetecting the user device within range of the network.

In accordance with additional aspects of this particular embodiment, theinformation required to provide delegate authority may comprise at leastprimary account holder identity information, primary account holderverification information, and delegate authority selection.

In accordance with other aspects of this particular embodiment, therequest for delegate authority may comprise at least one of an email, atext message, an instant message, a phone call, a voicemail, a website,a uniform resource locator (URL) link, and a menu window.

In accordance with further aspects of this particular embodiment,network access may comprise network access to at least one of acorporate network, enterprise network, residential network, and privatenetwork.

In another particular embodiment, the techniques may be realized as amethod for providing dynamic account and user device management. Themethod may comprise receiving a request for delegate authority by anentity to manage a user device. The method may comprise transmittinginformation required to provide delegate authority to manage the userdevice. The method may comprise receiving network access at the userdevice, wherein the entity manages the user device and monitors datacommunicated to and from the user device.

In accordance with other aspects of this particular embodiment, themethod may comprise providing identity of the user device to be managedby receiving a request by a user of the user device for network accessor detecting the user device within range of the network.

In accordance with further aspects of this particular embodiment, theuser device may be a personal user device associated with a personaluser account comprising at least one of: an Internet-based account, acloud-accessible account, and an enterprise-compatible account.

In accordance with additional aspects of this particular embodiment, theinformation required to provide delegate authority may comprise at leastprimary account holder identity information, primary account holderverification information, and delegate authority selection.

In accordance with other aspects of this particular embodiment, therequest for delegate authority may comprise at least one of: an email, atext message, an instant message, a phone call, a voicemail, a website,a uniform resource locator (URL) link, and a menu window.

In accordance with further aspects of this particular embodiment,network access may comprise network access to at least one of: acorporate network, enterprise network, residential network, and privatenetwork.

The present disclosure will now be described in more detail withreference to exemplary embodiments thereof as shown in the accompanyingdrawings. While the present disclosure is described below with referenceto exemplary embodiments, it should be understood that the presentdisclosure is not limited thereto. Those of ordinary skill in the arthaving access to the teachings herein will recognize additionalimplementations, modifications, and embodiments, as well as other fieldsof use, which are within the scope of the present disclosure asdescribed herein, and with respect to which the present disclosure maybe of significant utility.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to facilitate a fuller understanding of the present disclosure,reference is now made to the accompanying drawings, in which likeelements are referenced with like numerals. These drawings should not beconstrued as limiting the present disclosure, but are intended to beexemplary only.

FIG. 1 shows a block diagram depicting a network architecture forproviding dynamic account and device management in accordance with anembodiment of the present disclosure.

FIG. 2 depicts a block diagram of a computer system for providingdynamic account and device management in accordance with an embodimentof the present disclosure.

FIG. 3 shows a module for providing dynamic account and devicemanagement in accordance with an embodiment of the present disclosure.

FIG. 4 depicts a flowchart of a method for providing dynamic account anddevice management in accordance with an embodiment of the presentdisclosure.

FIG. 5 depicts a flowchart of a method for providing dynamic account anddevice management in accordance with an embodiment of the presentdisclosure.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

FIG. 1 shows a block diagram depicting a network architecture 100 forproviding dynamic account and device management in accordance with anembodiment of the present disclosure. FIG. 1 is a simplified view ofnetwork architecture 100, which may include additional elements that arenot depicted. Network architecture 100 may contain client systems 110,120 and 130, as well as servers 140A and 140B (one or more of which maybe implemented using computer system 200 shown in FIG. 2). Clientsystems 110, 120 and 130 may be communicatively coupled to a network150. Server 140A may be communicatively coupled to storage devices160A(1)-(N), and server 140B may be communicatively coupled to storagedevices 160B(1)-(N). Servers 140A and 140B may contain a managementmodule (e.g., management module 154 of server 140A). Servers 140A and140B may be communicatively coupled to a SAN (Storage Area Network)fabric 170. SAN fabric 170 may support access to storage devices180(1)-(N) by servers 140A and 140B, and by client systems 110, 120 and130 via network 150.

With reference to computer system 200 of FIG. 2, modem 247, networkinterface 248, or some other method may be used to provide connectivityfrom one or more of client systems 110, 120 and 130 to network 150.Client systems 110, 120 and 130 may be able to access information onserver 140A or 140B using, for example, a web browser or other clientsoftware (not shown). Such a client may allow client systems 110, 120and 130 to access data hosted by server 140A or 140B or one of storagedevices 160A(1)-(N), 160B(1)-(N), and/or 180(1)-(N).

Networks 150 and 190 may be local area networks (LANs), wide areanetworks (WANs), the Internet, cellular networks, satellite networks, orother networks that permit communication between clients 110, 120, 130,servers 140, and other devices communicatively coupled to networks 150and 190. Networks 150 and 190 may further include one, or any number, ofthe exemplary types of networks mentioned above operating as astand-alone network or in cooperation with each other. Networks 150 and190 may utilize one or more protocols of one or more clients or serversto which they are communicatively coupled. Networks 150 and 190 maytranslate to or from other protocols to one or more protocols of networkdevices. Although networks 150 and 190 are each depicted as one network,it should be appreciated that according to one or more embodiments,networks 150 and 190 may each comprise a plurality of interconnectednetworks.

Storage devices 160A(1)-(N), 160B(1)-(N), and/or 180(1)-(N) may benetwork accessible storage and may be local, remote, or a combinationthereof to server 140A or 140B. Storage devices 160A(1)-(N),160B(1)-(N), and/or 180(1)-(N) may utilize a redundant array ofinexpensive disks (“RAID”), magnetic tape, disk, a storage area network(“SAN”), an internet small computer systems interface (“iSCSI”) SAN, aFibre Channel SAN, a common Internet File System (“CIFS”), networkattached storage (“NAS”), a network file system (“NFS”), optical basedstorage, or other computer accessible storage. Storage devices160A(1)-(N), 160B(1)-(N), and/or 180(1)-(N) may be used for backup orarchival purposes.

According to some embodiments, clients 110, 120, and 130 may besmartphones, PDAs, desktop computers, a laptop computers, servers, othercomputers, or other devices coupled via a wireless or wired connectionto network 150. Clients 110, 120, and 130 may receive data from userinput, a database, a file, a web service, and/or an applicationprogramming interface.

Servers 140A and 140B may be application servers, archival platforms,backup servers, network storage devices, media servers, email servers,document management platforms, enterprise search servers, or otherdevices communicatively coupled to network 150. Servers 140A and 140Bmay utilize one of storage devices 160A(1)-(N), 160B(1)-(N), and/or180(1)-(N) for the storage of application data, backup data, or otherdata. Servers 140A and 140B may be hosts, such as an application server,which may process data traveling between clients 110, 120, and 130 and abackup platform, a backup process, and/or storage. According to someembodiments, servers 140A and 140B may be platforms used for backing upand/or archiving data. One or more portions of data may be backed up orarchived based on a backup policy and/or an archive applied, attributesassociated with the data source, space available for backup, spaceavailable at the data source, or other factors.

According to some embodiments, clients 110, 120, and/or 130 may containone or more portions of software for providing dynamic account anddevice management such as, for example, management module 154. Asillustrated, one or more portions of management module 154 may reside ata network centric location. For example, server 140A may be a server, afirewall, a gateway, or other network element that may perform one ormore actions to provide dynamic account and device management. Accordingto some embodiments, network 190 may be an external network (e.g., theInternet) and server 140A may be a gateway or firewall between one ormore internal components and clients and the external network.

Management module 154 may provide, among other things, dynamic accountauthority for delegated scope of control over software and devicemanagement for an enterprise or corporate entity. As described above,more and more companies are allowing employees to bring their personalcomputing devices to work and use them in the work environment. However,managing these personal devices and monitoring data communicated usingthese devices within a corporate setting is becoming increasinglychallenging, especially across multiple management systems and multipleaccounts.

A personal user account may define scope of control for a user and hisor her computing device. The personal user account may also definesoftware and services associated with the user or computing device. Forexample, a personal user account may contain a user profile, a useridentity, and/or other related user credentials. Other various items maybe registered to the personal user account as well. For example, one ormore devices, one or more applications (e.g., software applications),and/or services may be registered to the personal user account.Accordingly, when a user authenticates himself or herself with thepersonal account, the user may have access and control of devices,applications, and/or services registered to the personal user account.

In order for another entity (e.g., a business, employer, family member,etc.) to manage some or all of the devices, applications, and/orservices associated with the personal user account, that entity mayrequire some measure of authorization to access the personal useraccount. Such authority may be delegated to the entity by the user oraccount holder of the personal user account.

In order to provide such delegated authority, the management module 154may interact with a personal user account. In some embodiments, thepersonal user account may be an Internet-based, cloud-accessibleaccount, or enterprise-compatible account, although other types ofaccounts may be used as well.

The management module 154 may have device management capabilities. Themanagement module 154 may also have capabilities to add one or moreauthorized delegates to the personal user account. The one or moreauthorized delegate may be authenticated in various ways. For example,in some embodiments, the one or more authorized delegates may beauthorized by the personal user account. In other embodiments, the oneor more authorized delegates may be authorized by another authorizingaccount different from the personal user account. In other embodiments,the one or more authorized delegates may be authorized by some othertrusted identity or source.

In some embodiments, an owner or account holder of the personal useraccount may also grant access (e.g., entire or partial access) to his orher device associated with the personal user account before assigning adelegate, either by an authorizing account or identity authorizes thedelegate. For example, a user (e.g., employee) may desire to use his orher personal computing device in a corporate setting (e.g., employerentity) to check email and/or perform other work-related functions. Theuser may put in a request (e.g., with the Information Technology (IT)department of the employer entity) to have his or her personal computingdevice configured to operate in the corporate setting.

In response, the entity may send a communication to the owner or accountholder of the personal user account to authenticate the personal useraccount and register the entity as a delegate. For instance, the entitymay send an email having an embedded uniform resource locator (URL) linkto the owner or account holder of the personal user account toauthenticate the personal user account and register the entity as adelegate. The URL may direct the owner or account holder to a website ormenu window to verify him or herself as the owner or account holder andto delegate authority to the entity. Other various communications, suchas text message, instant message, phone call, and voicemail, may also beutilized.

In some embodiments, a delegate may be registered without use of emailwith URL link. For example, when a user brings his or her personal userdevice within a vicinity of a corporate network, the corporate networkmay detect the personal user device. Upon detection or upon use of thepersonal device within the vicinity of the corporate network, a window(e.g., a pop-up menu or other similar indicator) may be presented at theuser device so that the user of the device (presumably the owner oraccount holder of the personal user account) may authenticate thepersonal user account and register the entity associated with thecorporate network as a delegate.

Delegate authority may have a range of authority. For example, authoritygranted to the entity may be partial authority (manage some of thedevice functions, applications and/or services) or total authority(manage all of the device functions, applications and/or services). Itshould be appreciated that the level of authority granted to thedelegate may be customizable by the owner of the personal user account,by the policies and standards of the entity, by the capabilities of thedevice/account management system, or a combination thereof.

There may be several ways to provide delegated authority to a userdevice. One way may be to register explicit lists of networks for eachaccount delegate. Another way may be to associate a URL only availableon the corporate network (e.g., LAN) with the delegate. Here, themanagement module 154 of the user device may attempt to connect to theURL before granting the agreed upon control to the delegate account. Yetanother way may be to use network discovery mechanisms, such as the userdevice broadcast a request for local network specific management or alocal server notify new user devices of the requirement for localnetwork specific management. In some embodiments, server-pushednotifications may be a part of a dynamic host configuration protocol(DHCP) response or sent out of band in response to a DHCP request,antenna reference point (ARP) discovery, or other client networkactivity. Other various device or network discovery mechanisms may alsobe utilized.

It should be appreciated that in some embodiments, delegate authoritymay be granted or received within a directory-like service, where theremay be a single authority over all resources. Management systems usingthe same authority may have rights delegated in a static manner, e.g.,based on groups, roles, permissions, other similar way. In otherembodiments, the same authority may not be required. Rather, delegatedauthority may be dynamic and not based on role-based access control orother static parameters.

It should be appreciated that the management module 154 may utilizepublicly accessible application programming interfaces (APIs) tofacilitate delegate registration for managing accounts and associateddevices. It should also be appreciated that the owner or account holderof a personal user account and associated device may have power toterminate or revoke delegate authority. As a result, management module154 may provide dynamic account and device management without forfeitingend user control.

By providing dynamic account authority for delegated scope of controlover software and device management, managing personal user devices andmonitoring data communicated using these devices within a corporatesetting may become much easier. Allowing multiple management systems tohave authority to manage and monitor the same personal user devicedynamically may allow business entities (or families) an attractive wayto integrate use of personal user devices while still maintainingsufficient degree of control.

FIG. 2 depicts a block diagram 200 of a computer system for providingdynamic account and device management in accordance with an embodimentof the present disclosure. Computer system 200 is suitable forimplementing techniques in accordance with the present disclosure.Computer system 200 may include a bus 212 which may interconnect majorsubsystems of computer system 210, such as a central processor 214, asystem memory 217 (e.g. RAM (Random Access Memory), ROM (Read OnlyMemory), flash RAM, or the like), an Input/Output (I/O) controller 218,an external audio device, such as a speaker system 220 via an audiooutput interface 222, an external device, such as a display screen 224via display adapter 226, serial ports 228 and 230, a keyboard 232(interfaced via a keyboard controller 233), a storage interface 234, afloppy disk drive 237 operative to receive a floppy disk 238, a host busadapter (HBA) interface card 235A operative to connect with a FibreChannel network 290, a host bus adapter (HBA) interface card 235Boperative to connect to a SCSI bus 239, and an optical disk drive 240operative to receive an optical disk 242. Also included may be a mouse246 (or other point-and-click device, coupled to bus 212 via serial port228), a modem 247 (coupled to bus 212 via serial port 230), networkinterface 248 (coupled directly to bus 212), power manager 250, andbattery 252.

Bus 212 allows data communication between central processor 214 andsystem memory 217, which may include read-only memory (ROM) or flashmemory (neither shown), and random access memory (RAM) (not shown), aspreviously noted. The RAM is may be the main memory into which theoperating system and application programs may be loaded. The ROM orflash memory can contain, among other code, the Basic Input-Outputsystem (BIOS) which controls basic hardware operation such as theinteraction with peripheral components. Applications resident withcomputer system 210 may be stored on and accessed via a computerreadable medium, such as a hard disk drive (e.g., fixed disk 244), anoptical drive (e.g., optical drive 240), a floppy disk unit 237, orother storage medium. For example, management module 154 may be residentin system memory 217.

Storage interface 234, as with the other storage interfaces of computersystem 210, can connect to a standard computer readable medium forstorage and/or retrieval of information, such as a fixed disk drive 244.Fixed disk drive 244 may be a part of computer system 210 or may beseparate and accessed through other interface systems. Modem 247 mayprovide a direct connection to a remote server via a telephone link orto the Internet via an internet service provider (ISP). Networkinterface 248 may provide a direct connection to a remote server via adirect network link to the Internet via a POP (point of presence).Network interface 248 may provide such connection using wirelesstechniques, including digital cellular telephone connection, CellularDigital Packet Data (CDPD) connection, digital satellite data connectionor the like.

Many other devices or subsystems (not shown) may be connected in asimilar manner (e.g., document scanners, digital cameras and so on).Conversely, all of the devices shown in FIG. 2 need not be present topractice the present disclosure. The devices and subsystems can beinterconnected in different ways from that shown in FIG. 2. Code toimplement the present disclosure may be stored in computer-readablestorage media such as one or more of system memory 217, fixed disk 244,optical disk 242, or floppy disk 238. Code to implement the presentdisclosure may also be received via one or more interfaces and stored inmemory. The operating system provided on computer system 210 may beMS-DOS®, MS-WINDOWS®, OS/2®, OS X®, UNIX®, Linux®, or another operatingsystem.

Power manager 250 may monitor a power level of battery 252. Powermanager 250 may provide one or more APIs (Application ProgrammingInterfaces) to allow determination of a power level, of a time windowremaining prior to shutdown of computer system 200, a power consumptionrate, an indicator of whether computer system is on mains (e.g., ACPower) or battery power, and other power related information. Accordingto some embodiments, APIs of power manager 250 may be accessibleremotely (e.g., accessible to a remote backup management module via anetwork connection). According to some embodiments, battery 252 may bean Uninterruptable Power Supply (UPS) located either local to or remotefrom computer system 200. In such embodiments, power manager 250 mayprovide information about a power level of an UPS.

FIG. 3 shows a module 310 for providing dynamic account and devicemanagement in accordance with an embodiment of the present disclosure.Referring to FIG. 3, there is shown a management module 310 inaccordance with an embodiment of the present disclosure. As illustrated,the management module 310 may contain one or more components includingdevice and account management module 312, authentication module 314,communication and network module 316, and error logging and reportingmodule 318.

The description below describes network elements, computers, and/orcomponents of a system and method for providing dynamic account anddevice management that may include one or more modules. As used herein,the term “module” may be understood to refer to computing software,firmware, hardware, and/or various combinations thereof. Modules,however, are not to be interpreted as software which is not implementedon hardware, firmware, or recorded on a processor readable recordablestorage medium (i.e., modules are not software per se). It is noted thatthe modules are exemplary. The modules may be combined, integrated,separated, and/or duplicated to support various applications. Also, afunction described herein as being performed at a particular module maybe performed at one or more other modules and/or by one or more otherdevices instead of or in addition to the function performed at theparticular module. Further, the modules may be implemented acrossmultiple devices and/or other components local or remote to one another.Additionally, the modules may be moved from one device and added toanother device, and/or may be included in both devices.

Device and account management module 312 may manage one or more devicesand/or one or more accounts. These device and/or accounts may includepersonal user devices brought by a user (e.g., employee) and used withinspecific network (e.g., corporate network).

Authentication module 314 may manage various delegate authority anentity has over various personal user devices and/or personal useraccounts. Authentication module 314 may also coordinate with personaluser devices and/or personal user accounts to ensure delegate authorityis valid and up to date.

Communication and network module 316 may provide, among other things,various features, including, but not limited to single sign-on, devicedetection, device communication, and/or other network or communicationrelated functions and features.

Error logging and reporting module 318 may produce logs, reports, orother information associated with providing dynamic account and devicemanagement.

Each of the modules of the management module 310 may, singly orcollective, perform one or more of the functions required to providingdynamic account and device management as described herein.

FIG. 4 depicts a flowchart 400 of a method for providing dynamic accountand device management in accordance with an embodiment of the presentdisclosure. The exemplary method 400 is provided by way of example, asthere are a variety of ways to carry out methods disclosed herein. Themethod 400 shown in FIG. 4 may be executed or otherwise performed by oneor a combination of various systems. The method 400 is described belowas carried out by at least system 100 in FIG. 1, architecture 200 inFIG. 2, module 310 in FIG. 3, and schematic 400 of FIG. 4, by way ofexample, and various elements of systems 100, 200, 310, and 400 arereferenced in explaining the exemplary method of FIG. 4. Each blockshown in FIG. 4 represents one or more processes, methods, orsubroutines carried in the exemplary method 400. A non-transitorycomputer-readable medium comprising code, which when performed by acomputer, may perform the acts of the method 400 may also be provided.Referring to FIG. 4, the exemplary method 400 may begin at block 402.

At block 402, the method 400 may begin.

At block 404, the management module 310 may identify a user device to bemanaged using at least the device and account management module 312 orthe communication and network module 316. The user device may be apersonal user device associated with a personal user account. Thepersonal user account may comprise at least one of an Internet-basedaccount, a cloud-accessible account, and an enterprise-compatibleaccount.

In some embodiments, identifying the user device to be managed maycomprise receiving a request by a user of the user device for networkaccess. In other embodiments, identifying the user device to be managedmay comprise detecting the user device within range of the network.

At block 406, the management module 310 may transmit a request fordelegate authority to manage the user device using at least theauthentication module 314 or the communication and network module 316.In some embodiments, the request for delegate authority may comprise atleast one of an email, a text message, an instant message, a phone call,a voicemail, a website, a uniform resource locator (URL) link, and amenu window.

At block 408, the management module 310 may receive delegate authorityto manage the user device using at least the authentication module 314or the communication and network module 316. The delegate authority maybe granted or revoked by a primary accountholder of via the personaluser account.

At block 410, the management module 310 may provide network access tothe user device using at least the communication and network module 316.In some embodiments, the management module 310 may manage the userdevice and monitor data communicated to and from the user device usingat least the device and account management module 312. Network accessmay comprise network access to at least one of a corporate network,enterprise network, residential network, and private network.

At block 412, the method 400 may end.

FIG. 5 depicts a flowchart 500 of a method for providing dynamic accountand device management in accordance with an embodiment of the presentdisclosure. The exemplary method 500 is provided by way of example, asthere are a variety of ways to carry out methods disclosed herein. Themethod 500 shown in FIG. 5 may be executed or otherwise performed by oneor a combination of various systems. The method 500 is described belowas carried out by at least system 100 in FIG. 1, architecture 200 inFIG. 2, module 310 in FIG. 3, and schematic 400 of FIG. 4, by way ofexample, and various elements of systems 100, 200, 310, and 400 arereferenced in explaining the exemplary method of FIG. 5. Each blockshown in FIG. 5 represents one or more processes, methods, orsubroutines carried in the exemplary method 500. A non-transitorycomputer-readable medium comprising code, which when performed by acomputer, may perform the acts of the method 500 may also be provided.Referring to FIG. 5, the exemplary method 500 may begin at block 502.

At block 502, the method 500 may begin.

At block 504, the management module 310 may provide identity of the userdevice to be managed using at least the device and account managementmodule 312 or the communication and network module 316. In someembodiments, providing identity of the user device to be managed maycomprise receiving a request by a user of the user device for networkaccess. In other embodiments, providing identity of the user device tobe managed may comprise detecting the user device within range of thenetwork.

The user device may be a personal user device associated with a personaluser account. The personal user account may comprise at least one of anInternet-based account, a cloud-accessible account, and anenterprise-compatible account.

At block 506, the management module 310 may receive a request fordelegate authority by an entity to manage a user device using at leastthe authentication module 314 or the communication and network module316. In some embodiments, the request for delegate authority maycomprise at least one of an email, a text message, an instant message, aphone call, a voicemail, a website, a uniform resource locator (URL)link, and a menu window.

At block 508, the management module 310 may transmit informationrequired to provide delegate authority to manage the user device usingat least the authentication module 314 or the communication and networkmodule 316. The information required to provide delegate authority maycomprise at least primary account holder identity information, primaryaccount holder verification information, and delegate authorityselection. It should be appreciated that the delegate authority may begranted or revoked by a primary accountholder of via the personal useraccount.

At block 510, the management module 310 may receive network access atthe user device using at least the communication and network module 316.In some embodiments, receive network access at the user device alsocomprises the management module 310 managing the user device andmonitoring data communicated to and from the user device using at leastthe device and account management module 312. Network access maycomprise network access to at least one of a corporate network,enterprise network, residential network, and private network.

At block 512, the method 400 may end.

At this point it should be noted that providing dynamic account anddevice management in accordance with the present disclosure as describedabove typically involves the processing of input data and the generationof output data to some extent. This input data processing and outputdata generation may be implemented in hardware or software. For example,specific electronic components may be employed in a management module orsimilar or related circuitry for implementing the functions associatedwith providing dynamic account and device management in accordance withthe present disclosure as described above. Alternatively, one or moreprocessors operating in accordance with instructions may implement thefunctions associated with providing dynamic account and devicemanagement in accordance with the present disclosure as described above.If such is the case, it is within the scope of the present disclosurethat such instructions may be stored on one or more processor readablestorage media (e.g., a magnetic disk or other storage medium), ortransmitted to one or more processors via one or more signals embodiedin one or more carrier waves.

The present disclosure is not to be limited in scope by the specificembodiments described herein. Indeed, other various embodiments of andmodifications to the present disclosure, in addition to those describedherein, will be apparent to those of ordinary skill in the art from theforegoing description and accompanying drawings. Thus, such otherembodiments and modifications are intended to fall within the scope ofthe present disclosure. Further, although the present disclosure hasbeen described herein in the context of a particular implementation in aparticular environment for a particular purpose, those of ordinary skillin the art will recognize that its usefulness is not limited thereto andthat the present disclosure may be beneficially implemented in anynumber of environments for any number of purposes. Accordingly, theclaims set forth below should be construed in view of the full breadthand spirit of the present disclosure as described herein.

The invention claimed is:
 1. A method for providing dynamic account anduser device management comprising: transmitting a request for delegateauthority to manage a personal electronic user device within atelecommunications network in response to receiving a request from theuser device for access to the network; receiving from the user devicedelegate authority to manage the user device; and managing the userdevice and monitoring data communicated to and from the user devicewithin the network in accordance with a level of authority delegated bythe user device.
 2. The method of claim 1, wherein the user device isassociated with a personal user account comprising at least one of anInternet-based account, a cloud-accessible account, and anenterprise-compatible account.
 3. The method of claim 2, wherein thedelegate authority is granted by a primary accountholder of the personaluser account.
 4. The method of claim 1, further comprising: identifyingthe user device to be managed.
 5. The method of claim 4, whereinidentifying the user device to be managed comprises receiving a requestby a user of the user device for network access.
 6. The method of claim4, wherein identifying the user device to be managed comprises detectingthe user device within range of the network.
 7. The method of claim 1,wherein the request for delegate authority comprises at least one of anemail, a text message, an instant message, a phone call, a voicemail, awebsite, a uniform resource locator (URL) link, and a menu window. 8.The method of claim 1, further comprising: providing network access tothe user device.
 9. The method of claim 8, wherein the network accesscomprises network access to at least one of a corporate network,enterprise network, residential network, and private network.
 10. Themethod of claim 1, wherein the delegate authority comprises a range ofauthority.
 11. The method of claim 10, wherein the range of authoritycomprises partial or total authority, wherein the range of authority iscustomizable based on at least one of an owner of the user device, anaccount holder of the user device, policies and standards of an entityrequesting delegate authority, and capabilities of an management systemof the entity.
 12. A system for providing dynamic account and userdevice management comprising: one or more processors communicativelycoupled to a network, wherein the one or more processors are configuredto: transmit a request for delegate authority to manage a personalelectronic user device within a telecommunications network in responseto receiving a request from the user device for access to the network;receive from the user device delegate authority to manage the userdevice; and manage the user device and monitoring data communicated toand from the user device within the network in accordance with a levelof authority delegated by the user device.
 13. The system of claim 12,wherein the user device is associated with a personal user accountcomprising at least one of an Internet-based account, a cloud-accessibleaccount, and an enterprise-compatible account.
 14. The system of claim13, wherein the delegate authority is granted by a primary accountholderof the personal user account.
 15. The system of claim 12, wherein theone or more processors are configured to: identify the user device to bemanaged.
 16. The system of claim 15, wherein identifying the user deviceto be managed comprises receiving a request by a user of the user devicefor network access.
 17. The system of claim 15, wherein identifying theuser device to be managed comprises detecting the user device withinrange of the network.
 18. The system of claim 12, wherein the requestfor delegate authority comprises at least one of an email, a textmessage, an instant message, a phone call, a voicemail, a website, auniform resource locator (URL) link, and a menu window.
 19. The systemof claim 12, wherein the one or more processors are configured to:provide network access to the user device.
 20. The system of claim 19,wherein the network access comprises network access to at least one of acorporate network, enterprise network, residential network, and privatenetwork.
 21. The system of claim 12, wherein the delegate authoritycomprises a range of authority.
 22. The system of claim 21, wherein therange of authority comprises partial or total authority, wherein therange of authority is customizable based on at least one of an owner ofthe user device, an account holder of the user device, policies andstandards of an entity requesting delegate authority, and capabilitiesof an management system of the entity.
 23. An article of manufacture forproviding dynamic account and user device management, the article ofmanufacture comprising: at least one non-transitory processor readablestorage medium; and instructions stored on the at least one medium;wherein the instructions are configured to be readable from the at leastone medium by at least one processor and thereby cause the at least oneprocessor to operate so as to: transmit a request for delegate authorityto manage a personal electronic user device within a telecommunicationsnetwork in response to receiving a request from the user device foraccess to the network; receive from the user device delegate authorityto manage the user device; and manage the user device and monitoringdata communicated to and from the user device within the network inaccordance with a level of authority delegated by the user device.